home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
ram315.zip
/
RAMAIL.DOC
< prev
next >
Wrap
Text File
|
1993-02-02
|
26KB
|
566 lines
▒██████ ▒██████ ▒██ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒███ ▒███ ▒█████ ▒██ ▒██
▒██████ ▒██████ ▒████▒████ ▒██ ▒██
▒██ ▒█ ▒██ ▒██ ▒██▒███▒██ ▒█████ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒██ ▒█ ▒██ ▒██▒██ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒██ ▒██ ▒██████ ▒██ ▒██
Release 3.15
Copyright 1990-1992 by Randy Blackmond
All Rights Reserved
Page 1 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
INTRODUCTION
────────────
Welcome to RAMail (pronounced 'are ay mail'), the mail system exclusively
for RemoteAccess(c). RAMail is a door which allows your users to select
messages of their choice and download them for offline reading. In
addition, users can upload messages which are unarchived and imported
into your message base. Files can be tagged and downloaded at the same
time from your BBS file directories. Internal transfer protocols are
provided for X/Y/ZModem. External protocols may also be added.
SYSTEM REQUIREMENTS
───────────────────
. IBM compatible computer with 640K RAM, DOS 3.X and above.
. RA 1.11
NOTE: RAMail 3.15 will run with RA 1.01 and 1.10, but the System Info
function will display garbage. You can disable the System Info
function using RAMCONF if you are still running RA 1.01 or 1.10.
FILES INCLUDED IN THE RAMAIL31 ARCHIVE
──────────────────────────────────────
INSTALL.DOC - Installation notes
RAM.BAT - Example batch file for the door
RAMAIL.DOC - The main documentation (this file)
RAMCONF.DOC - The documentation for the Config program, RAMCONF.EXE
RAMUSRED.DOC - The documentation for the RAUSER.DAT Editor, RAMUSRED.EXE
NS-PORTS.DOC - Special instructions when using non-standard COM ports
CNFCVT31.EXE - The CFG file conversion utility for upgrading from 3.0
NEWRAU31.EXE - The RAUSER.DAT conversion utility for upgrading from 3.0
RAMAIL.EXE - The executable door program
RAMCONF.EXE - The executable configuration program
RAMUSRED.EXE - The executable RAUSER.DAT editor
RAURPT.EXE - RAUSER.DAT Report Utility
RAURPT.DOC - The documentation for RAURPT
RAM31REG.DOC - Registration form for RAMail 3.15
RAMWELC.A?? - Welcome screen files
RAMMENU.A?? - Main Menu screens
RAMAIL.HLP - Online Help file
RANEWUSR.A?? - Sample New User screens
RAMNEWS.A?? - Sample News screens
DOOR.ID - Door identifier used by SLMR and possibly other readers
BETATEST.NFO - Beta Tester information for future versions of RAMail
THE READER
──────────
The RAMail Door is only half of the complete system. The other half
is a reader. You, as a sysop, don't need a reader for your door to
function, but your users will so they can read and reply to the mail
in the packets the door produces. I recommend The Silly Little Mail
Reader, but Session Manager, Qmail or EZ-Reader will also work.
Page 2 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
UPGRADE INSTALLATION
────────────────────
3.1 Upgrade
If you are upgrading from RAMail 3.1, simply copy the 3.15 files over
the old ones.
3.0 Upgrade
If you are upgrading from RAMail 3.0, first run CNFCVT31.EXE in the
directory where your RAMail CFG file resides. Repeat for each CFG file
if you have more than one. Next, run NEWRAU31.EXE in the directory where
your RAUSER.DAT file resides. Replace your 3.0 RAMAIL.EXE, RAMCONF.EXE
and the RAMUSRED.EXE with the files inside the 3.15 archive. Run RAMCONF
and fill in the new fields (see RAMCONF.DOC). Set the DSZLOG environment
variable if you are using DSZ (or GSZ) as your external protocol engine.
If you have a trailing backslash on your RA environment variable, e.g.
C:\RA\, remove it! RA does not need it and RAMail expects it to NOT be
there.
Pre-3.0 Upgrade
If you are upgrading from a version of RAMail prior to 3.0, you must
delete your RAMail CFG files and your RAUSER.DAT file. Run RAMCONF to
recreate your RAMail CFG file. Copy the ANS/ASC/HLP files to your RA
TXTFILES directory. Set the DSZLOG environment variable if you are
using DSZ (or GSZ) as your external protocol engine.
If you have a trailing backslash on your RA environment variable, e.g.
C:\RA\, remove it! RA does not need it and RAMail expects it to NOT be
there.
FIRST TIME INSTALLATION
───────────────────────
Unpack the RAMail archive and move all the ANS/ASC/HLP files to
your RA TXTFILES directory. Next, move the remaining files to
your RA system directory, usually called C:\RA (or create a
separate directory and move them in). If you choose to run from RAMail's
own directory, you will need to modify and use the RAM.BAT file
to run from a Type 7 menu selection.
Finally, run the configuration program to create an RAMAIL.CFG file.
You must supply the name of the CFG file you wish to create/edit on the
command line with RAMCONF, e.g. RAMCONF RAMAIL.CFG. The fields are
described in RAMCONF.DOC. Set the DSZLOG environment variable if you
are using DSZ (or GSZ) as your external protocol engine.
If you have a trailing backslash on your RA environment variable, e.g.
C:\RA\, remove it! RA does not need it and RAMail expects it to NOT be
there.
Page 3 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
MULTI-LINE OPERATION
────────────────────
To set up RAMail in a multinode environment, put the RAMAIL.EXE,
RAMCONF.EXE, and RAMUSRED.EXE files in your DOS path. Create an
RAMAIL.CFG file for each node in the RA node directories. For example:
C:\RA - ramail.exe, ramconf.exe, ramusred.exe
C:\RA\NODE1 - ramail.cfg
C:\RA\NODE2 - ramail.cfg
The only differences between the config files is the directories in
which RAMail will look for the EXITINFO.BBS files. Node 1 is then run
from C:\RA\NODE1, and Node2 from C:\RA\NODE2. RAMail will create the
.QWK packets in the appropriate work directory. The .REP packets will
also end up in the separate work directories.
EXTERNAL SUPPORT FILES
──────────────────────
Except where noted, all files listed below use the ASC/ANS extension
convention for BBS display files and must reside in your RA TextFiles
directory. All are optional except where noted.
RAMWELC.A* - This file is displayed to the user upon entering the door.
RANEWUSR.A* - This file is displayed to a user after the welcome screen
the first time he enters the door.
RAMNEWS.A* - This file is displayed to all users after the opening
welcome screen.
RAMMENU.A* - The RAMail menu. These files are REQUIRED.
RAMAIL.HLP - The Help file is REQUIRED.
DOOR.ID - This file is used by SLMR and possibly other readers
to determine from which mail door the packet came. It
should reside in your RA system directory.
All external display files used by RAMail support some of the more common
control codes used by RA. These include clear screen, pause, user name and
others. Attempts to use an unsupported code will result in N/A being dis-
played. See RA.DOC for an explanation of these codes.
There is a file included with the RAMail package named DOOR.ID. This file
is used by SLMR to determine which mail door created the packets. Simply
place the file in your RA system directory and RAMail will include it in
all QWK packets automatically.
Page 4 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
TYPE 7 MENU SETUP
─────────────────
Put RAMAIL.EXE, RAMAIL.CFG, and DOOR.ID in your RA system
directory. The Type 7 menu entry for RAMail should be as follows:
Optional Data: RAMAIL.EXE RAMAIL.CFG *M
or
*C /C RAM.BAT *M
You should use RA's swapping to ensure there is enough memory for RAMail
to run. To do this put *M after RAMAIL.EXE RAMAIL.CFG on your Optional
Data line. Failure to do so will probably result in not enough memory
being available for RAMail to run.
TYPE 15 MENU SETUP
──────────────────
First, create a directory on your hard drive in which RAMail will reside.
Place RAMAIL.EXE, RAMAIL.CFG and DOOR.ID into that directory.
Modify RAM.BAT to your own directory names.
@echo off
cd \RA\RAMAIL
RAMAIL RAMAIL.CFG
cd \RA
Note that the name of the CFG file you created is passed to RAMAIL.EXE on
the command line. Also, ANSI.SYS or some facsimile must be loaded to
enable you to see the ANSI colors the door uses locally. Loading ANSI.SYS
is not necessary for successful operation of the door, however.
Place the batch file in your RA directory and add the door to your menu
the same way you add any level 15 door.
USAGE
─────
The Main Menu for RAMail is straightforward. The options are:
Conference Select, Download, Upload, File Areas, Page, System Info,
Bulletin Toggle, Transfer Protocol, Help, New Files, Express Mail Run,
Include New Files Toggle, ANSI Toggle, Packing Method, Restore Pointers,
Modify Pointers, Quit and Goodbye.
CONFERENCE SELECTION allows your users to decide which message boards they
wish to be included in their downloaded mail. It will display all avail-
able message boards and allow them to pick which ones they want. The con-
figuration the user chooses will be saved in a mini user file maintained
by RAMail, RAUSER.DAT). They can change their configuration at any time.
Users will not be allowed to choose boards for which they do not have a
high enough security level and/or a set Read Flag to read.
Page 5 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
The DOWNLOAD option extracts all new mail for the configuration the user
has chosen and places them in a compressed packet and then invokes a send
of the packet.
The UPLOAD option invokes reception of a reply packet that will be named
[BBSCODE].REP. It will then uncompress the packet and import the replies
to your message files where they will be available immediately for
reading.
The FILE AREAS option allows users to view your file lists and flag files
to be downloaded with their mail packet. Checking is done to ensure the
user has access to a given file area according to security level and flag
settings. Full support of LIMITS.CTL is provided automatically as well.
The maximum number of files a user can flag for download is 5. This option
can be disabled in RAMCONF.
The PAGE option allows the user to page the Sysop for a chat. This option
can be disabled in RAMCONF. After a chat session is complete, the screen
is redrawn in black and white (non-ANSI) regardless of the user's ANSI
toggle setting. This is NORMAL. Redrawing in ASCII is much easier and
requires less code overheard than does an ANSI redraw. If the user does
have ANSI enabled, the ANSI screens will resume with the next function
the user performs.
The SYSTEM INFO option displays message stats, total calls and last caller
information. This option can be disabled in RAMCONF.
The BULLETIN TOGGLE allows the user to enable/disable the inclusion of
new bulletins in his/her mail packet.
The TRANSFER PROTOCOL option allows the user to select a download protocol
to be used when performing mail/file transfers. This option is initially
set to the first defined protocol for new users.
The HELP option will display the file RAMAIL.HLP. You can use the included
file or create your own.
The NEW FILES option will search all available file directories for files
newer than (or equal to) the date of the user's last call and list them to
the screen. This option can be disabled in RAMCONF.
The EXPRESS MAIL RUN option will cause RAMail to create the mail packet
and then immediately send it. Upon completion of the transfer, the user
will be logged off after a 10 second logoff abort opportunity.
The INCLUDE NEW FILES TOGGLE option enables/disables the new files scan
that RAMail performs during packet creation.
The ANSI Toggle allows the user to turn ANSI off and on. Any change
made remains effective only while in the RAMail door.
The PACKING METHOD option allows the user to choose which of the 3
compression methods that you have configured to be used when processing
mail packets, ZIP, ARJ, OR LZH.
The MODIFY POINTERS option allows the user to set ALL Last Read pointers
simultaneously to a new value.
Page 6 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
The RESTORE POINTERS option restores a user's pointers to the state they
were in before the user's previous download. Note that if you renumber
your messages, the saved pointers will then be invalid until the user
downloads his next packet. The purpose of this option is to allow the
user to recover from trashed packets due to things such as CRC errors and
corrupt files.
The QUIT option returns the user to the BBS.
The GOODBYE option disconnects the caller and exits the door.
REMOTE CONFERENCE SELECTION
───────────────────────────
Users can select the board configuration they want by entering special
offline messages. If a message is addressed to RAMAIL or QMAIL the
subject will determine the configuration action to be taken. The choices
for the subject are as follows:
ADD - Adds a conference and selects all mail
ADD A - Adds a conference and selects all mail
ADD Y - Adds a conference and selects your mail only
ADD YA - Adds a conference and selects your mail and mail to All
DROP - Drops a conference
NETMAIL
───────
Netmail messages can be entered by placing NET> followed immediately by
the zone:net/node address on the first line of the message, e.g.
NET>1:381/70
The message board that the message is imported to must be a NetMail
board.
Page 7 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
HISTORY
───────
1.0 Initial release of RAMail!
1.1 Increased the speed of the message export process TREMENDOUSLY!
200 message packets should be created in about 30 seconds or so.
Did away with the idea of conference pointers. There's just no
feasible way to do something like that with RA. The last read
message pointer will be read from the user's record upon entry
into RAMail and updated after downloading a packet.
1.2 This version was released as a fix for the problem of the last read
message pointer not being updated. Too bad it didn't fix it!
1.3 Discovered reason for the read pointer not being updated (I thought)
Added different message download limits for each baud rate (See
INSTALLATION). Added Hot Keys.
1.4 Finally! An enhancement version! The Configuration option has been
enhanced to allow the user to elect to receive only their mail and
mail addressed to All or All mail. Added the Modify Last Read
Pointer option. Added optional RACONFS.LST board name file. Last
Read Message Pointer problem was finally solved!
1.5 Stomped a few more bugs. Added FIDO Default Origin line support for
messages uploaded to an EchoMail board. Increased packet processing
speed even more. RA's message indexes are automatically updated by
RAMail when replies are uploaded. New RAMCONF program eases creation
and modification of your RAMAIL.CFG file(s). Added support for
multiple nodes. RAMail should now work properly on boards where the
message files reside in their own directory. Much more!
2.0 Still more bugs stomped. Should now be completely FIDO compatible.
Added Files feature, Your Mail Only mail selector, high ASCII filter
option for FIDO boards, Personal Mail support, New Files and New
Bulletins support, Default Protocol, Online Help, Goodbye from the
menu or after transfer and more!
2.01 Maintenance release. The message attributes set by RAMail were all
messed up resulting in such problems as imported EchoMail messages
not being marked as pending export and private messages not being
marked or recognized as private.
2.1 Added path for RAUSER.DAT in RAMCONF.EXE. This was to allow multiple
node systems to use the same RAUSER.DAT file for all nodes. Added
(S)elect All and (D)eselect All in the configuration option.
2.2 Added support for the DOOR.ID file that SLMR 2.0 will make use of.
Added offline mail configuration support. RAMail will write to your
system log(s) when mail/files are download/uploaded. Origin lines
are attached to incoming echo mail only if Echo Info is enabled in
your RACONFIG. Stomped a few bugs.
Page 8 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
3.0 Netmail support added. Reader taglines in Echomail and Netmail
boards can be stripped. Several menu options can now be turned off
if desired. Several external display screens have been implemented.
Compression/decompression and protocol programs are now fully
configurable. A new page-oriented conference select screen is now
used. Users can select to receive their own messages on a per
conference basis when in C)onference Select. And MORE!
3.1 Internal transfer protocols added. Work directories added.
NetStatus capability added for use in QWK networks in conjunction
with MKNet(c). Bulletin names (up to 30) are configurable within
RAMCONF. Export speed increased. And MORE!
3.15 A little work done on the internal protocols in an attempt to
eliminate the lockup problems on some systems. Whether or not
I was successful remains to be seen. Lockups caused by a missing
DSZLOG environment variable when using DSZ or GSZ have been
eliminated. Instead of locking up, a little reminder message is
displayed and the transfer result is determined by the errorlevel
returned from DSZ. The reason I use the DSZLOG environment variable
instead of the code is that the errorlevel method does not always
work! Added Handle check during mail extraction. Now, any mail
addressed to your name or your handle will be seen as personal mail.
A sneaky little bug that appeared when an error occurred before work
directory creation caused all files in the current directory to be
deleted! This has been corrected. Flagged files were not being
detected by the internal protocols. This has been fixed. Added a
little to the docs in an attempt to make the crucial setup points
more clear and visible.
DISCLAIMER
──────────
As stated before, all reasonable precautions have been take to ensure
that your system files will not be damaged, but if any damage does
occur caused by RAMail either directly or indirectly, I will not
be held responsible for such damages. USE THIS PRODUCT AT YOUR OWN RISK!
CREDITS
───────
This Door was written with JPDOOR 3.01 Copyright 1991 by Rod Hancock
PKZIP/PKUNZIP is Copyright 1989-1991 by PKWARE, Inc.
LHA is Copyright 1988-1991 by Haruyasu Yoshizaki
ARJ is Copyright 1990, 1991 by Robert K. Jung
DSZ is Copyright 1991 by Omen Technology INC
QuickBBS is Copyright 1990 by The QuickBBS Group, Inc.
RemoteAccess is Copyright 1991 by Continental Software
Session Manager is copyright 1991 by Patrick Hart
EZ-Reader is copyright 1988-1991 by Thumper Technologies
Qmail is copyright 1987-1991 by Sparkware
MKNet is copyright 1991 by Mark May
Silly Little Mail Reader is copyright 1991 by Greg Hewgill and
Computer Techniques
Page 9 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
And special thanks to the beta testers for their patience, support and
wonderful suggestions!
PROBLEMS & SUGGESTIONS
──────────────────────
Bug reports, problems, suggestions and comments can be made to Randy
Blackmond in the RIME/RelayNet Doors, Sysops, Shareware or RA conference,
The FIDONet RA Utilities echo, NetMail to 1:381/70 or call Randy's
Basement BBS 1200/2400/9600 USR DS at (505) 589-0319. I can also be
reached voice at 505-589-0317.
COMMON ERROR CODES:
2 File Not Found
Check all paths in your RAMail configuration.
3 Path Not Found
Check all paths in your RAMail configuration.
100 Disk Read Error
This can result if you have an invalid RAUSER.DAT or
invalid RAMAIL.CFG file. Delete one or both and start over.
Will also occur if you are running a version of RA prior
to 1.01. You MUST be running at least RA 1.01, preferably
RA 1.11!
101 Disk Write Error
Results from a full disk. Free some disk space.
COMMON PROBLEMS AND SOLUTIONS
─────────────────────────────
Problem: File transfers are always reported as aborted!
Solution: Set your DSZLOG environment variable (see DSZ.DOC).
Problem: After an uploaded reply packet has been received, RAMail
locks up!
Solution: You must have the RA environment variable and the DSZLOG
environment variable set!
Problem: RAMail does not run on my system AT ALL!
Solution: You do not have enough memory for RAMail to run in. Add the
*M on your Optional Data line if you are using a type 7
setup. If you are using a type 15 setup and still have this
problem, you either have too many TSRs loaded or you are
running in too small of a multitasking window.
Problem: The mail packets are created fine, but when the transfer
procedure begins, it always aborts.
Solution: You probably have an error in your protocol definition in
your RAMail configuration. Unless you REALLY know what you
are doing, you should use the DSZ defaults provided by
RAMCONF or stick to the internal protocols.
Page 10 RAMail v3.15
──────────────────────────────────────────────────────────────────────────
Problem: The external protocols work ok, but the internal protocols
always lock up at the end of a transfer.
Solution: Try following the directions in the included NS-PORTS.DOC,
even if you are using COM1 or COM2. If this does not solve
the problem, disable the internal protocols and use only
the externals.
Problem: A user who uses Session Manager complains of messages being
listed in the wrong conference.
Solution: Session Manager has some problem with RAMail packets. To
resolve it, when loading SM, do it in this manner:
SM /FI /TC